Hello!

In my laptop with Windows 8.1 Prof. I'm trying to create Internal switch and receive following error:

"Failed while creating virtual Ethernet switch.

Switch create failed, name ='<GUID>', friendly name = 'New Virtual Switch'^ There is no driver selected for the device information set or element (0x800F0203)."

Some time ago (maybe before 8.1 update, not sure) I successfully created external switch and it works well.

Please, help me to resolve the issue.

Hi Sir,

Did you installed any anti-virus software in windows 8.1 host ?

If yes , please uninstall it then check the result .

If the issue persists , I would suggest you to perform in-place upgrade with Win8.1 OS media .

Best Regards,

Elton Ji

Hi Sir,

Did you installed any anti-virus software in windows 8.1 host ?

If yes , please uninstall it then check the result .

If the issue persists , I would suggest you to perform in-place upgrade with Win8.1 OS media .

Best Regards,

El

Have you tried deleting the existing virtual switch and creating a new one?

If you updated to 8.1 from 8, that could be the issue and it may have corrupted your virtual switch.

Hi Sir,

>What do you mean "in-place upgrade with Win8.1 OS media"? Should I re-install the OS over existing one?

"An in-place upgrade is the final alternative before you have to reinstall the operating system"

https://support.microsoft.com/en-us/kb/2255099?wa=wsignin1.0

Best Regards,

Elton Ji

Have you tried deleting the existing virtual switch and creating a new one?

If you updated to 8.1 from 8, that could be the issue and it may have corrupted your virtual switch.

Hi Sir,

Did you try to perform an in-place upgrade for W8.1 ?

Best Regards,

Elton Ji

Hi Sir,

Did you try to perform an in-place upgrade for W8.1 ?

Best Regards,

El

Before you do, perhaps you should try a few other steps:

• Use DISM /Online /Cleanup-Image /RestoreHealth to verify the integrity of core system files.
• Check for any network adapters that are improperly configured in Device Manager, if so delete them and restart to allow Windows to relocate drivers for the device. Be sure to enable hidden devices from the View menu.
• Verify that you have vmswitch.sys in C:\WINDOWS\System32\DRIVERS\.

Brandon
Windows Outreach Team- IT Pro
Windows for IT Pros on TechNet

Before you do, perhaps you should try a few other steps:

• Use DISM /Online /Cleanup-Image /RestoreHealth to verify the integrity of core system files.
• Check for any network adapters that are improperly configured in Device Manager, if so delete them and restart to allow Windows to relocate drivers for the device. Be sure to enable hidden devices from the View menu.
• Verify that you have vmswitch.sys in C:\WINDOWS\System32\DRIVERS\.

Brandon
Windows Outreach Team- IT Pro
Windows for IT Pros on TechNet

Hi Brandon! Thank you for the tips!

vmswitch.sys is present there.

In the device manager I had several unknown devices under Other Devices. I deleted them all. When I tried to add virtual network switch I received the same error and new unknown device was added. Also I have few devices with question mark: My printer, Lightweight Sensors Root Enumerator, Microsoft RRAS Root Enumerator, Send To OneNote 2013.

The DISM utility ended with error: Error: 0x800f0906 The source files could not be downloaded (log attached). The SFC /scannow also finished with error: Windows Resource Protection found corrupt files but was unable to fix some of them (log attached).

CBS.log

DISM.log

When I tried to add virtual network switch I received the same error and new unknown device was added.

Try adding a Legacy adapter instead?

FWIW I'm in this same mess since an update screwed up my Hyper-V Networking.  I'm still trying to determine if  NVSPScrub is going to help or make things worse and before that I'm going to try understanding what  NVSPBind is seeing.

https://social.technet.microsoft.com/Forums/en-US/e331b0f1-2b29-4093-9cc0-8c30a7ffc932/help-me-get-my-vms-networking-going-again-after-a-w812-update-screwed-it-up?forum=w8itprovirt

The DISM utility ended with error: Error: 0x800f0906

That just shows you have the currently known telemetry issue.  Nothing to worry about.

HTH

Robert, thank you for reply.

I have no problems with adapters. I have troubles with adding new virtual switch.

I have no problems with adapters. I have troubles with adding new virtual switch.

I have no problems with adapters. I have troubles with adding new virtual switch.

Then please detail the procedure and where it breaks.  In my case there is no trouble adding a switch--at least an Internal one.  The problem comes when I try to "fill it in" or if that worked then usin

In the form with new switch details I click OK and error occurs.

There should be an event log message about that.  If necessary you could also add to it with some tracing but I don't have a specific suggestion for which provider to try.  But I imagine that it has already gone through its troubleshooter for you?  If so, capture the detailed log from that and just read it for clues.  Reading it using SysInternals streams program is just a convenience of not having to scan though double-byte text.

Also, did you see the help page that I found and mentioned in my thread?

Actually I thought I had remembered reading something about multiple switches there but couldn't find what I was thinking about (although there are lots of hints elsewhere at that site about the advisability of only having one).

Instead you have just made me discover that my PowerShell has features I didn't know it had

http://www.altaro.com/hyper-v/virtual-switch-hyper-v-server-2012/ 

<quote>

Rule #1: Unless you are very clear on what the defaults are and what youre going

to get, dont use the GUI.
</quote>

PS>get-help *-vmswitch

Name                              Category  Module                    Synopsis
----                              --------  ------                    --------
Add-VMSwitch                      Cmdlet    Hyper-V                   Add-VMSwitch...
Get-VMSwitch                      Cmdlet    Hyper-V                   Get-VMSwitch...
New-VMSwitch                      Cmdlet    Hyper-V                   New-VMSwitch...
Remove-VMSwitch                   Cmdlet    Hyper-V                   Remove-VMSwitch...
Rename-VMSwitch                   Cmdlet    Hyper-V                   Rename-VMSwitch...
Set-VMSwitch                      Cmdlet    Hyper-V                   Set-VMSwitch...

E.g. previously I had given up after not finding Remove-VMSwitch.  Perhaps I had been looking after one of my attempts at disabling the Hyper-V feature.  Who knows, anyway, it's good to know that I do have it.

Ugh.  It doesn't help me get rid of my broken one.  YMMV.

Try using the New-VMSwitch cmdlet instead of the GUI?  Actually there could be another good reason to try to doing that.  You might be able to get better diagnostics that way too than what the GUI provides, even after its troubleshooter is run.

Good luck

Robert, the error is the same if I use PowerShell instead of GUI.

Elton, so recently I tried both the feature re-activating and Windows in-place upgrade. Both failed :(

@ Ivan

I got further on my problem symptom.  Now at least I can use the VM in a Homegroup.  There have been so many changes being tested getting there that I can't give specific advice but I think this may have been accomplished while my Wi-Fi connection was disconnected but the Wireless adapter was not disabled.  I had not noticed before that there could be this distinction.  Also, there are some new PowerShell commands I rely on to see what the state of the connections is.

Get-NetConnectionProfile

That consistently shows I have an "Unidentified network" with "NoTraffic" for both IPv4 and IPv6.  The troubleshooters always set it to Public even when I want to use the Homegroup, when at least the IPv6 one must be Private.  There are two ways to work around this irritant.  One, which I knew about before, is to use the Homegroup troubleshooter but bypass its not so helpful suggestion to try using the Networking troubleshooter first.  That allows you to then see its necessary suggestion to make the connection Private.  The second new way is another PowerShell command related to the above:

Set-NetConnectionProfile  -NetworkCategory "Private"

There are some other parameters for that cmdlet but (evidently) they are only used to help us filter out a particular connection to apply that change to.  If only we could change the "NoTraffic" state this way too...   ; }